Properties fields

Use properties fields in →FBD to specify properties (e.g. requirements) at any position within the function logic.

A properties field is similar to a →comment field. Observe the following differences:

  • For a better distinction, the properties fields are displayed with a different color than the comment fields.

  • A property statement must be entered within the property field – analogous to the property statements in ST but without the enclosing characters: { }; of ST.
    See the following representation for an example. In case of another input, it is not possible to exit the input mode of the property field.

  • The content of a properties field is transferred to the generated code as comment.

Representation

Example for a properties field with one requirement:

(info) It is possible to enter several lines within a property field. See "Creating or editing properties fields in FBD" for the syntax.

(info) Depending on the configuration of your Neuron Power Engineer version, the FBD-editor and its elements might be displayed differently in your Neuron Power Engineer version than illustrated in the IDE documentation. This is the case, if Neuron  or the system integrator has activated the smart styling or one of them has changed the styles for the FBD-editor. Subsequently, the illustration in the IDE documentation are symbolic images and the representation in your Neuron Power Engineer version takes precedence for the valid representation. In case of doubts, please contact Neuron or your system integrator.

Neuron recommends that you and/or your system integrator do not use yellow shades when designing FBD-elements because the color "Yellow" is used for tracking safe signals when developing safety-related applications. This recommendation applies in particular when you are using the legacy styling. Neuron Power Engineer does not check if colors are already used elsewhere. So the use of the yellow shades by you and/or your system integrator could have the consequence that "yellow" might also identify a non-safe logic as well.

Actions for properties fields